pointerA11yTimeout: Adapt to API changes in Mutter

https://gitlab.gnome.org/GNOME/mutter/-/commit/76166d61 did sneak
in an API change by removing the ClutterInputDevice arguments from
the ClutterSeat::ptr-a11y-timeout-* signals. Through a series of
astonishing coincidences, we don't use those arguments, so just
remove them. Since the rest of the arguments were shifted, this
fixes broken behavior of the PieTimer.

Closes: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/8654
Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3877>

diff --git a/js/ui/pointerA11yTimeout.js b/js/ui/pointerA11yTimeout.js
index 0b2eef5066d92347fc90d2156f3ce80714fab964..6a9ceca662f22e982b373482c8bca436ae307787 100644 (file)
--- a/js/ui/pointerA11yTimeout.js
+++ b/js/ui/pointerA11yTimeout.js
@@ -112,7 +112,7 @@ export class PointerA11yTimeout {
     constructor() {
         const seat = global.stage.context.get_backend().get_default_seat();
 
-        seat.connect('ptr-a11y-timeout-started', (o, device, type, timeout) => {
+        seat.connect('ptr-a11y-timeout-started', (o, type, timeout) => {
             let [x, y] = global.get_pointer();
 
             this._pieTimer = new PieTimer();
@@ -125,7 +125,7 @@ export class PointerA11yTimeout {
                 global.display.set_cursor(Meta.Cursor.CROSSHAIR);
         });
 
-        seat.connect('ptr-a11y-timeout-stopped', (o, device, type, clicked) => {
+        seat.connect('ptr-a11y-timeout-stopped', (o, type, clicked) => {
             if (!clicked)
                 this._pieTimer.destroy();